-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add a11y no-noninteractive-element-to-interactive-role
#8167
feat: add a11y no-noninteractive-element-to-interactive-role
#8167
Conversation
2f2956c
to
14a3131
Compare
no-noninteractive-element-to-interactive-role
@ngtr6788 is attempting to deploy a commit to the Svelte Team on Vercel. A member of the Team first needs to authorize it. |
As noted in #8251 (comment), could you keep the boolean methods (making them simple wrapper methods of your new enum-returning methods)? This would reduce the things changed and (IMO) makes the code a bit more readable on the usage side. Code looks good otherwise! |
Sounds good! I just pushed the wrapper method you mentioned now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This has been released in 3.57.0 - thank you! |
You're welcome! |
sveltejs#8167 introduced the strict version of it - until this is configurable, we should use the relaxed version instead, since many a11y docs actually advise using ul/ol etc
Hey everyone, this is my first time contributing to the Svelte project as well as open source in general. 👋
I noticed that there are a few accessibility checks remaining in #820 and I picked up no-noninteractive-element-to-interactive-role (not to be confused by no-interactive-element-to-noninteractive-role, which was already done #5955).
However, I have a small question: There are cases where this rule doesn't apply if we set it under eslint-jsx recommended settings but is applied under strict settings. Are we using the strict settings here? (edited because I asked another question and already found the answer)
My test plan:
Let me know if there are improvements or comments you want to make!
Before submitting the PR, please make sure you do the following
[feat]
,[fix]
,[chore]
, or[docs]
.Tests
npm test
and lint the project withnpm run lint